Skip to content

Rename slime references to vime - #121

Merged
CalvinXKY merged 17 commits into
mainfrom
chore/rename-slime-to-vime-clean
Jun 4, 2026
Merged

Rename slime references to vime#121
CalvinXKY merged 17 commits into
mainfrom
chore/rename-slime-to-vime-clean

Conversation

@aoshen02

@aoshen02 aoshen02 commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Rename non-acknowledgement slime/SLIME/Slime references to vime/VIME/Vime across docs, scripts, CI, issue templates, and code identifiers
  • Update repository and docs links from THUDM/slime to vllm-project/vime
  • Keep the README acknowledgement references to the slime community as requested

Verification

  • git diff --check
  • git diff --name-only -z -- '*.py' | xargs -0 ../../.venv/bin/python -m py_compile
  • git diff --name-only -z -- '*.sh' | xargs -0 bash -n
  • Confirmed remaining slime matches are only README acknowledgement lines

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request performs a comprehensive renaming of the framework from 'slime' to 'vime' across documentation, scripts, and codebase comments. The reviewer's feedback correctly points out several instances where renaming 'slime' to 'vime' is problematic, such as creating circular statements (e.g., 'vime is derived from vime'), breaking external links to upstream pull requests, making upstream issue references untraceable, and incorrectly modifying 'upstream slime' references in the backend engine code. All of these comments are valid and should be addressed by reverting those specific renames.

Comment thread CONTRIBUTING.md Outdated
## About vime

**vime** is a reinforcement learning (RL) post-training framework built on [**vLLM**](https://github.com/vllm-project/vllm) and [**Megatron-LM**](https://github.com/NVIDIA/Megatron-LM) as its core backends. It is derived from [slime](https://github.com/THUDM/slime).
**vime** is a reinforcement learning (RL) post-training framework built on [**vLLM**](https://github.com/vllm-project/vllm) and [**Megatron-LM**](https://github.com/NVIDIA/Megatron-LM) as its core backends. It is derived from [vime](https://github.com/vllm-project/vime).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The project is derived from the upstream slime framework. Renaming this reference to vime creates a circular statement ('vime is derived from vime'). Please keep the reference to slime here.

Suggested change
**vime** is a reinforcement learning (RL) post-training framework built on [**vLLM**](https://github.com/vllm-project/vllm) and [**Megatron-LM**](https://github.com/NVIDIA/Megatron-LM) as its core backends. It is derived from [vime](https://github.com/vllm-project/vime).
**vime** is a reinforcement learning (RL) post-training framework built on [**vLLM**](https://github.com/vllm-project/vllm) and [**Megatron-LM**](https://github.com/NVIDIA/Megatron-LM) as its core backends. It is derived from [slime](https://github.com/THUDM/slime).

Comment thread CONTRIBUTING.md Outdated
## 关于vime

**vime**是以[**vLLM**](https://github.com/vllm-project/vllm)与[**Megatron-LM**](https://github.com/NVIDIA/Megatron-LM)为核心后端的RL后训练框架,源自[slime](https://github.com/THUDM/slime)。
**vime**是以[**vLLM**](https://github.com/vllm-project/vllm)与[**Megatron-LM**](https://github.com/NVIDIA/Megatron-LM)为核心后端的RL后训练框架,源自[vime](https://github.com/vllm-project/vime)。

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The project is derived from the upstream slime framework. Renaming this reference to vime in the Chinese documentation creates a circular statement. Please keep the reference to slime here.

Suggested change
**vime**是以[**vLLM**](https://github.com/vllm-project/vllm)[**Megatron-LM**](https://github.com/NVIDIA/Megatron-LM)为核心后端的RL后训练框架,源自[vime](https://github.com/vllm-project/vime)
**vime**是以[**vLLM**](https://github.com/vllm-project/vllm)[**Megatron-LM**](https://github.com/NVIDIA/Megatron-LM)为核心后端的RL后训练框架,源自[slime](https://github.com/THUDM/slime)

Comment thread docs/en/advanced/reproducibility.md Outdated
```

For screen shots of the wandb, please refer to [pull#370](https://github.com/THUDM/slime/pull/370).
For screen shots of the wandb, please refer to [pull#370](https://github.com/vllm-project/vime/pull/370).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The pull request #370 refers to the original PR in the upstream THUDM/slime repository where the wandb screenshots are located. Changing this link to vllm-project/vime will break the reference as PR #370 does not exist on the new repository. Please keep the original link to the upstream repository.

Suggested change
For screen shots of the wandb, please refer to [pull#370](https://github.com/vllm-project/vime/pull/370).
For screen shots of the wandb, please refer to [pull#370](https://github.com/THUDM/slime/pull/370).

Comment thread docs/zh/advanced/reproducibility.md Outdated
```

这个 PR 中记录了 wandb 的截图 [pull#370](https://github.com/THUDM/slime/pull/370)。
这个 PR 中记录了 wandb 的截图 [pull#370](https://github.com/vllm-project/vime/pull/370)。

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The pull request #370 refers to the original PR in the upstream THUDM/slime repository where the wandb screenshots are located. Changing this link to vllm-project/vime will break the reference as PR #370 does not exist on the new repository. Please keep the original link to the upstream repository.

Suggested change
这个 PR 中记录了 wandb 的截图 [pull#370](https://github.com/vllm-project/vime/pull/370)
这个 PR 中记录了 wandb 的截图 [pull#370](https://github.com/THUDM/slime/pull/370)

Comment thread docker/Dockerfile Outdated
Comment on lines +86 to +88
# torch_memory_saver pinned to a193d9dd (upstream vime #1916). The newer commit
# ships a multi-CUDA wheel and requires TMS_CUDA_MAJOR at build time; default it
# to the running torch's CUDA major (slime #1924).
# to the running torch's CUDA major (vime #1924).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

These comments refer to specific issues/PRs (#1916 and #1924) in the upstream THUDM/slime repository. Changing them to vime makes them untraceable. Please keep the references to slime here.

# torch_memory_saver pinned to a193d9dd (upstream slime #1916). The newer commit\n# ships a multi-CUDA wheel and requires TMS_CUDA_MAJOR at build time; default it\n# to the running torch's CUDA major (slime #1924).

Comment thread vime/backends/vllm_utils/arguments.py Outdated
# heterogeneous per-group engines (different num_gpus_per_engine). TP is resolved per engine
# in ``vllm_engine._resolve_vllm_parallel_sizes`` (tp = gpus_per_engine // pp), mirroring
# upstream slime's sglang_engine. (pp divisibility is validated there, per engine.)
# upstream vime's sglang_engine. (pp divisibility is validated there, per engine.)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This comment refers to the upstream slime project's sglang_engine. Since slime is the upstream project, the term 'upstream slime' is correct. Please revert this change to keep the reference accurate.

Suggested change
# upstream vime's sglang_engine. (pp divisibility is validated there, per engine.)
# upstream slime's sglang_engine. (pp divisibility is validated there, per engine.)

Comment thread vime/backends/vllm_utils/vllm_engine.py Outdated

def _resolve_vllm_parallel_sizes(args, *, gpus_per_engine: int) -> tuple[int, int]:
# Derive TP per-engine from THIS engine's GPU count (matches upstream slime's
# Derive TP per-engine from THIS engine's GPU count (matches upstream vime's

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This comment refers to the upstream slime project's sglang_engine. Since slime is the upstream project, the term 'upstream slime' is correct. Please revert this change to keep the reference accurate.

Suggested change
# Derive TP per-engine from THIS engine's GPU count (matches upstream vime's
# Derive TP per-engine from THIS engine's GPU count (matches upstream slime's

@aoshen02
aoshen02 force-pushed the chore/rename-slime-to-vime-clean branch from aa7e58c to 96a947e Compare June 2, 2026 13:59
@aoshen02
aoshen02 force-pushed the chore/rename-slime-to-vime-clean branch from 96a947e to 85f7354 Compare June 3, 2026 01:59
@CalvinXKY

Copy link
Copy Markdown
Collaborator
image

@CalvinXKY
CalvinXKY merged commit 9524dd5 into main Jun 4, 2026
10 of 13 checks passed
@aoshen02
aoshen02 deleted the chore/rename-slime-to-vime-clean branch June 8, 2026 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants